Silk Mobile
Table of Contents (Homepage)
- Overview
- Setting Up
- Getting Started
- How To
- Connecting Devices And Emulators
- Preparing Applications For Testing
- Managing Applications
- Recording Tests
- Working With Test Commands
- Adding Commands To Your Scripts
- Object Commands
- Click
- ClickCoordinate
- ClickIn
- ClickOffset
- Drag
- ElementGetProperty
- ElementGetTableRowsCount
- ElementListPick
- ElementListSelect
- ElementListVisible
- ElementScrollToTableRow
- ElementSendText
- ElementSetProperty
- ElementSwipe
- ElementSwipeWhileNotFound
- GetAllValues
- GetElementCount
- GetElementCountIn
- GetTextIn
- IsElementBlank
- IsElementFound
- IsFoundIn
- LongClick
- RunNativeAPICall
- SendWhileNotFound
- VerifyElementFound
- VerifyElementNotFound
- VerifyIn
- WaitForElement
- WaitForElementToVanish
- GetCoordinateColor
- DragDrop
- Application Commands
- Device Commands
- Web (Hybrid) Specific Commands
- Utilities Commands
- Monitoring Commands
- Configuration Commands
- ExtractLanguageFiles
- SetDefaultClickDownTime
- SetDefaultTimeOut
- SetDefaultWebView
- SetDragStartDelay
- SetInKeyDelay
- SetKeyToKeyDelay
- SetLanguage
- SetLanguagePropertiesFile
- SetShowImageInReport
- SetShowPassImageInReport
- SetShowReport
- SetSpeed
- SetThrowExceptionOnFail
- SetWebAutoScroll
- StartStepsGroup
- StopStepsGroup
- TextFilter
- Miscellaneous Commands
- Controlling Element Identification Rules
- Editing Test Objects
- Executing Test Scripts
- Report Of Executed Test
- Working From Code Environment
- Continuous Integration
- Layout Verification Tests
- Use Device Vitals Monitors
- Troubleshooting
- Terminology
Dynamic NATIVE Recognition
|
|
|
|
User can use Native recognition method with the following options:
-
After application preparation: Preparing Native/Hybrid Applications for Testing
-
Using non instrumented mode: Non-Instrumented Native Recognition
-
Using the object spy mode: Using the Reflection's Control Buttons
Step 1: Once choosing zone Native for command.
Step 2: Use the Spy icon button to get the Native properties of all the elements on the screen. Mark the required element and you will see in a pop-up box all the Object/Element Native properties.
Step 3: Use these properties to identify the element dynamically to perform the action on it. Build a query on the form: <query>=<value> or use xpath syntax.
Advanced
nclick:
In this case the event will be sent to the element directly instead of by its coordinates
The syntax is nclick:<query>=<value>